Datalogger with EK-TM4C129EXL

*** LIKE ***    Vendor's Ralph - in my firm's book - is "On Fire!"

Ralph Jacobi said:

If short range wireless to transfer data to a smartphone is an option...

May we ask - does "TIDA-00524" (as you've listed) provide guidance for the "Smartphone Side" software?    (likely required to display the data sent via, "short range wireless.")     Such would make your suggestion (even) more compelling - both to this poster - and "many" others...    Android preferred...

Hi Ralph,

Bit "hard to keyboard" wearing asbestos-lined gloves - due to the "hotness" of one vendor agent...

Firm/I have acquired batches of, "very low cost" cell-phones - yet possessing "terrific, hi-contrast 4" Touch-screens."

Have to check to see if (by luck) these accommodate "NFC." (maker is Alcatel, Model A466BG - might your, "Being in NFC land" enable you to determine if this phone handles "NFC?")

Such would be greatly appreciated ... and likely useful to (multiple) others here (seeking an eased means to display MCU acquired/processed data...)

Great posts - thank you, Ralph...

Hello there

The optimal choice (if such exists) for that project depends on a few more pieces of information. At least, data rate required, data storage size, data storage location (is the "datalogger" just a bridge to have everything on the smartphone, or shall it keel data in it?), environmental limits...

A very simple solution just "ready to go" is the combination of a CC2650 Sensortag, and for for viewing values directly in the node, the DevPack LDC which goes with it.

Output will be limited to BLE rates, but that is certainly enough for humidity and temperature real needs. And you will get other readings immediately to play with, such as luminosity, pressure, and some others I can't recall at the moment.

Regards

Bruno

Hi Kel,

As you direct poster to be "clear" in his "preference" - perhaps you can assist your direction by, "Summarizing the various "strengths/weaknesses" of the various wireless techniques" you have presented.

Preference is - most always - uncertain/suspect - w/out proper knowledge...

I would suspect that a proper "wireless technology summary" would include:

• expected transmission range
• cost
• reliability/robustness (i.e. "BER" Bit Error Rate - as just one measure...)
• complexity - (both) HW & SW
• availability

It is noted that you've, "drawn devices from (only) a (very) narrow pool."     Might (other) vendor devices (LARGE Pool) engage nicely w/poster's TM4C MCU - possibly, "Speeding, Easing, Enhancing" his effort?    Is only the (hoped for) "speed & ease" of a "booster-pack" the (proper) "Driving Decision?"    (it must be noted that "often" these do not serve as, "Direct/Unmodified Plug-IN.")

Hi cb1,

    The TI CC3100 Booster Pack uses SPI to communicate with EK-TM4C129EXL. The BOOSTXL-SENSORS uses I2C to communicate with EK-TM4C129EXL.

    I have checked with TI Cloud Booster Pack Checker Too, that if I connect TI CC3100 Booster Pack and BOOSTXL-SENSORS to one Booster Pack connector of EK-TM4C129EXL the SPI and I2C pins do not conflict.

    It is possible to connect the TI CC3100 Booster Pack and BOOSTXL-SENSORS stacked on top of one Booster Pack connector of EK-TM4C129EXL.

    For LCD, I suggest the Sharp LCD Booster Pack. I have used Sharp LCD Booster Pack with EK-TM4C1294XL. So, it should work also with EK-TM4C129EXL.

- kel

Thank you, Markel. It remains "difficult to explain" then - why "so many arrive here" - unable to quickly/easily succeed when using these "booster-packs."

Convenience - when and if, "mostly a mirage" - proves not the best path for many users... (as reported here ... you surely recall the "horrors" encountered w/the exosite app. - and that just one example...)

Ralph Jacobi said:

Hello Naeemul,

If you want to show data on an LCD screen and your project allows you to have a completed project using EVM's not made by yourself, you might find the DK-TM4C129X even more interesting (albeit pricier) for your design as it already has an LCD screen on board.

What wireless communication were you thinking of using? If short range wireless to transfer data to a smartphone is an option, and you don't HAVE to support iOS you might find the following TI design quite interesting! www.ti.com/.../TIDA-00524 However if you require iOS I'm afraid that such a design wouldn't quite work due to Apple's pesky stances about NFC tech.

And yes you would need to buy a separate EVM/BoosterPack for Wireless. There are multiple options to choose from though, so you may want to clarify which wireless tech you want/need to use.

In general I'd recommend browsing http://www.ti.com/tidesignsto see what designs are available that may overlap with what you need so you can piece together a full solution. I certainly would encourage tackling it one step at a time too. Get the sensors you want first and foremost and figure those out, and then move to more complex technologies like LCD and wireless comms.

Thank u Ralph for the reply. I am actually thinking of using BLE since I want a long range to transfer data. As for iOS or Android, I haven't decided that yet; as u mentioned "One step at a time".

naeemhcl said:

as u mentioned "One step at a time".

That's one method - but would not, "One small, isolated, systematic, considered & measurable) step" - prove far better?    

That describes "KISS" (curiously banned here) - but not from those, "Seeking the fastest, most secure/efficient & robust" path to success!    ("step" (alone) - minus dictates/discipline of KISS - pales in comparison!)

Markel Robregado said:

Hi cb1,

I have some experience with WiFi and BLE so I will comment on those. But for much detailed information about WiFi and BLE, I suggest OP check in the internet.

Radio Frequency.
WiFi - 2.4 GHz
BLE - 2.4 GHz

Range
WiFi - 150 ft.
BLE - 328 ft.

Reference Design Tiva Connected Launchpad + TI CC3100 SimpleLink Wifi Booster Pack - Available

- http://www.ti.com/lit/ug/swru371b/swru371b.pdf
- Tiva Connected Launchpad + CC3100 BP example program available at Tivaware
- Able to log sensor data to Windows PC and Android Phone using WiFi Connectivity - Yes

Reference Design Tiva Connected Launchpad + TI BLE CC2650MODA Booster Pack - None

- Need to port code from MSP430 Launchpad + TI BLE CC2650MODA Booster Pack Example Program
- Able to log to Android Phone then send to data to Cloud Server. Data can be retrieved/seen using Web Browser

Since, there is reference design and example program for Tiva Connected Launchpad + TI CC3100 SimpleLink Wifi Booster Pack, I suggest OP
choose this for logging data to Windows PC or Android Phone.

Note Tiva Connected Launchpad(EK-TM4C1294XL) is similar board with Tiva Crypto Connected Launchpad(EK-TM4C129EXL)

EK-TM4C129EXL has 2 Booster Pack connectors. So, OP can connect LCD at Booster Pack Connector 1, TI CC3100 BP at Booster Pack Connector 2, Sensor Board with Temperature and Humidity Sensor connected at the bottom side of either booster pack connectors.

Relevant Boards:

1. EK-TM4C129EXL
2. TI CC3100 Booster Pack
3. BOOSTXL-SENSORS - with Bosch BME280 Environmental sensor - pressure, ambient temperature and humidity

- kel

As cb1 mentioned, you have actually saved me from the confusion of selecting the right booster packs. 

The last part of the comment mentions the three boards that I think I can work with. However, does using CC3100 booster pack means that I have to send data to the windows machine using WiFi? What I am thinking is basically send the real time data to both Windows and Android, but only store the data in the windows machine - in the HDD in my desktop. I don't think I can incorporate the cloud storage technology right now since this is a university project and I have time constraints. And if I wanna see the data of a week earlier, I will just pull it up from the HDD. 

naeemhcl said:

... send the real time data to both Windows and Android, but only store the data ...  in the HDD in my desktop.  I don't think I can incorporate the cloud storage technology right now ...

Bravo!     SO very wise & considered.    

And (of course) you are following the discipline of "KISS" - going for, "Simple & Sure" (although still w/challenge) and rejecting those areas of "Uncertainty & High RISK!"

Later (if ever) is the time for "improvements & battles w/Risk."     Achieve your "mission critical" objectives - as quickly & easily as possible - via a systematic, sequential, "One measurable/considered Step" at a time.    (and that of course - is "KISS!")

cb1 r u referring to KISS as Keep It Short and Simple??

naeemhcl said:

The last part of the comment mentions the three boards that I think I can work with. However, does using CC3100 booster pack means that I have to send data to the windows machine using WiFi? What I am thinking is basically send the real time data to both Windows and Android, but only store the data in the windows machine - in the HDD in my desktop

The Tiva Crypto Connected Launchpad + CC3100 SimpleLink WiFi, will send data to your PC through WiFi Router. I suggest your review the CC3100 documentations. You can also ask about this at SimpleLink WiFi Forum for more expert advice.

- kel

Bruno Saraiva said:

It is interesting that there are so many references to KISS on this thread, and yet no one seems to have read the suggestion of using a CC2650 Sensortag.

Might that have resulted due to, "Inadequate PROMOTION of the, "Features, Functions, Benefits" provided (uniquely) by that device - and the (too often) "inflexibility" & "limitations" imposed by the "hobby-class" restrictions (so often) imposed by such.

If there IS a quick/eased/robust/cost-effective means to "Exchange Data - In BOTH Directions" between an ARM MCU board (ideally our custom board) AND our volume/discounted Alcatel cell-phones - "We ARE ON THAT!"

Is this your recommendation, Bruno?    Can you (or vendor's Ralph) speak w/more detail re "CC2650 (or another) ability to provide TWO-WAY Commo between ARM MCU board & Alcatel cell-phone?    (these phones support both wi-fi & BT.

We do appreciate & thank you - for this alert - although (as you know) "Devil ALWAYS, "Lies/Lives in the Detail..."

Thank you, Bruno.    That said,

Bruno Saraiva said:

if it is an Android phone with Bluetooth Low Energy

Is this "BLE" (low energy) a STRICT Requirement - especially for the cell-phone?     Such may be a "gotcha" - and yours (here/now) was the first mention of "such restriction."

As stated - we seek to exploit the many benefits resulting from a, "Ready to Go, High Quality Display w/Touch-Screen, advanced ARM MCU, Android Marshmellow 6.0, 32GB memory - AND wi-fi and BT - all packaged, assembled & tested - and acquired at a FRACTION of the price we'd pay for "individual components - and their (exacting) assembly!"

As you noted - the "existing sensors" on your recommended board hold no interest - if we can "access the phone's advanced ARM MCU" - via BT, wi-fi, or wired (USB) we (and users here) - seeking "reduced cost/easily interfaced similar" are (very) FAR AHEAD!    (the device serves very much as an, "Advanced & Advantaged PRODUCT NUCLEUS - suitable for SO MANY APPLICATIONS - especially due to the price advantage!)

cb1_mobile said:

Is this "BLE" (low energy) a STRICT Requirement - especially for the cell-phone?

Yes, for the CC2650MOD it is.

I would assume that all current smartphones are BLE. And a few pieces that are 2-3 years old which I got my hands on were as well.

BLE is "totally different" from legacy, or "traditional" Bluetooth. It is focused on low energy consumption, and limited to "only so many bytes a second" (I won't bother writing the details here, it is certainly enough for using the remote phone/device as an HMI, and even to transport 5 to 10Hz data of "a few sensors" to be displayed on a live screen). We are currently pushing it to the "legal limit", and it works just fine.

For what is worth, "future Bluetooth" is BT 5, an increase of bandwidth while still at low power requirements - but that one is not for the "right now" products.

Bruno