When deploying a API in a scalable environment we usually try tom implement a stateless solution to avoid parallelism conflicts between the different nodes.
This works well for event management synchronously executed. But in some case these event need to have a part of the work managed asynchronously. It was my was my case when I had to process alarm report potentially generating multiple communications with execution time not predictable. To manage this I decided to process theses operation asynchronously. There are multiple architecture for managing this like Queuing (my preferred) of dedicate asynchronous engine. I’ve in fact preferred another way to do it for keeping my infrastructure more simple : adding in all of my nodes a batch function processing the alarms asynchronously.
The alarm events are written into the database and processed by the first of the batch taking it. This allow to preserve a fully redundant and simple architecture. That said I need to ensure only one of the process will execute this process at a time and potentially split the work to do between all the nodes. For making this I had to create a mutex solution.
This post describes the way to create a Mutex solution based on MongoDB with Spring Boot.
SpringBoot is a really efficient framework for creating webservices and much more. For this reason I’m using it to design my backend applications.
This framework is also well referenced on Internet and many people are downloading it and using it. All of this sounds really good and you will see you can make a webservice in less than 5 minutes following the many examples existing on Internet. As usually in this kind of technology once you have made the classical HelloWorld and university classical practices you have a lot of difficulties to make your first real program coupling different simple use-cases. So As I spent a couple of hours searching solution on Internet, this post will give you a full example of a project getting data from a MongoDB instance to provide a simple webservice.
Here is the situation : you have a function in an archive but you do not have the source code. And you would like to change the behavior of this function or intercept the call to this function.
This is possible with gcc and the -Wl,-wrap linker options. Thanks to this option you can create a new function starting by __wrap_ followed by the function name. This function will be called instead of the original one. In the function you can decide to call the original function by using its name starting by __real_
New version of the Telecom design SDK has been released for TD1208 / TD1208R / TD1204 and now officially supporting TD1205.
This new version provide some bug fixes, like a crash after 21285 transmissions that could be after 212 days in case of full use… some I had in touch with could be interested… @pioupiou and also a bug that disable gpio interrupt after sigfox transmission (I experimented it !)
For the main evolution, this version is supporting FCC and TD1508 and improving sigfox transmissions.
From my experience, this version is also a good way to decrease the size of your binary files.
This post is about upgrading from a SDK 5 to SDK6 and the impact you can when recompiling your projects.
To install the SDK from scratch, just follow the well documented official post here.
The revolution slider is a way to animate a web page based on a wordpress plugin. When you create a slider it start to be animated directly when the page is loaded. So if your slider is on top of the page it is perfect but if your animation is on the middle / bottom, the animate will be finished when the user will scroll to that part.
I previously write this post on how to use a BeagleBoneBlack as a JTAG (SWD) programmer. It was fun but really slow. I port my code on RaspberryPI and now what was taken 5-8 hours is a couple of minutes.
To connect the SWD connector to the PI use the following schema
I use this peace of code to reflash my TD1204 and TD1208 based both on EFM32 when bricked after unsuccessful update…
When you plan to deploy / sell sigfox based solution to consumer, you have to manage you device park. The sigfox network have a restricted radio medium to ensure you will not emit more than what you payed for you will be charged by them if a device you own is emitting, even if it is emitting out of your control. There is no network subscription like in 3G before being able to emit so anyone can emit. That is why, to ensure every one is clear, you have an extra cost if you emit more than you are allowed or if you emit from a non registered device.
When you are designing end-user system you have no control on the device and if you propose a monthly fee to use your solution you will never sure the end user will unplug it once he stop to pay for your service. It means you could have a consumer stopping to pay for your service but a device continuing to emit and sigfox request you to pay for it.
Since the network allow you to have downlink message, now you have the capability to send order to your device and as a consequence allowing you to kill the device remotely. This is a good solution !
Next you have a new scenario where your end user finally decide to reuse your service and want to reactivate the device. At this step you won’t be able to communicate with it and you will have to find another way to reset its state to normal. You can eventually add a “factory reset” button or request to reflash it. There is another funny when : playing with the reboot time.
This post will describe how to lock a device to stop emit on network and how to play with the startup sequence to reset it. Read more !
Are you looking for connecting an object ?
Based on BLE, Wifi, Sigfox, GSM, RF433?
IngeniousThings, my company, is able to help you on your IoT design, creativity, business model and provides quick prototypes. We are specialists for helping startups with LoRaWan and SigFox design.
You can also contact me here