A usual question you have when designing a device is the autonomy of your battery and the power consumption of your device. By the past I’ve tried different tools for this usage. Starting with USB sticks power consumption, only working for high consuming devices. They are low precision. Going to multimeter tools with USB connectivity precise but sampling at 3-5Hz only. During a certain time I’ve plan to make a solution on my own and finally I’ve found the OTII tool from QOITECH on the recommendation of friends from Sigfox community.
Here is my experience with that tool.
When making an IoT project the battery choice is something really important. Batteries stands for autonomy, sizing, price and usage conditions.
There is no universal solution to power your device, the right battery really depends on your requirements. To find the right powering solution you need to consider a certain number of parameters. We will try in this post to list most of them. This post is not exhaustive: I’m not a battery expert. This post is based on my own experience and you may consider it as a starting point, not a solution.
As it is a recurrent question to find the right battery for an IoT design, I decided to write a post about this topic. I’m not claiming to be an expert of this and I’ll not give insight on this. The purpose is to list the different technology existing with the main characteristics to be able to use the best fitting technologies quickly.
This post is presenting a table of the different battery’s technologies available with the main characteristics. These characteristics are global one regarding the technology. Each of the battery vendor can have specific specifications a bit different. You will need to take a look on datasheets details.
Murata CMWX1ZZABZ chip is actually famous for being a powerful LoRaWan multi zone module also able to communicate over Sigfox.
I’ve already published a technical post on Murata CMWX1ZZAB chip in a previous post. You will also find an implementation based on my IoT SDK. Yadom has just released a breakout board ( BRKABZ01) for this chip making it accessible for hackers and for easier prototyping.
This post is going to review this board and demo how to access it really quickly. Are you ready ?
I’m actually working on a device using a NFC chip from ST. Unfortunately, this chip is not using the ISO-14443 norms but the less usual ISO-15693 one. As a consequence the NFC reader I had were not compatible with this norms. I found a solution (there are not a lot) in Amazon to covert this need. The Fongwah S9 NFC Reader. I made this post to share my test experience of this device.
Precision: this is not a post made for Fongwah, I really have to crash my head on this device and the purpose of this post is to save your time. The fondwah S9 is a nice tool with a multi-language (on top of C library) SDK but it is delivered with no easy documentations, broken links and no reference on ISO-15693 support… I was a bit disappointed once the box opened.
Posted in Hardware
Tagged IoT, linux, NFC
ST Micro-Electronics is providing a development board with a Murata CMWX1ZZABZ-091 chip. This device is a module containing a STM32L0 chip (192Kb of Flash / 20Kb of RAM) associated with a Semtech SX1276 radio chip. This module can be used as a SoC for developing LoRaWan IoT devices. The Semtech chip is also capable of Sigfox. This module is a bit expensive but it is actually the one allowing LoRaWan and Sigfox communication in any of the RCZ zones.
STM32 solution for using Sigfox is actually one of the best offer on the market has the solution is powerful, low consumption and allows global coverage with the use of the last Sigfox library versions including Monarq, Bubble… Different module providers are actually designing solutions based on this platform.
In this post we are going to see how to configure the STM32 platform, starting from a STM32L053 devkit plus a S2LP extension. Using a eclipse/gcc environment. The environment installation is described in this post about installing Eclipse for STM32.
STM32 ARM MCU are proposing different low power mode for saving energy when running IoT on battery. Some basic example of low power are delivered with the SDK as part of CubeMx solution but these example are not really complete, not well documented and in my point of view difficult to use in a Fresh new project. Basically my current feeling with STM32 is these guy are pretty good to write thesis on how to do magic stuff with the MCU, writing hundreds of pdf pages about really detailed stuff but they are really bad for providing some line of code to illustrate this valuable content with something practicable you can use on the go. So after spending a week working on a working and understood example of low power code, I’ll share with you the result of this work…