developer developing iot

The short introduction (⚠️ Alert, geeky content below ⚠️)

On this page, you will meet our working process, tools, and technologies that we use every day. Every segment of new product development is important in its own way. We are up to date with new technology solutions in the field of communication, microprocessors, cloud, and other IoT segments.

What software tools do we use?

This is actually a pretty complex question. For most purposes, we use IDE’s made by JetBrains (PHP Storm, IntelliJ, etc.) but of course, there is a huge plethora of tools used in development. If we are talking about PIC32 microcontrollers then we are using Microchip’s Harmony Framework and MPLAB X IDE, which is based on Netbeans. Sometimes we do use mikroC PRO compiler by Mikroelektronika. Some prototyping and development tools have their own IDE’s, like Arduino IDE for Arduino, and mbed Compiler for mbed or Nucleo (STM32). For hardware, we are using various tools available, and our team members can choose a tool that fits their needs.

developer coding iot
hardware for iot

What hardware do we use?

For prototyping, we mostly use PIC32 development boards by OLIMEX, but sometimes we love to use straightforward libraries and features of well-known platforms like Arduino, mbed, and Raspberry Pi. Most of our products are based on Microchip technology (PIC or PIC32) but based on project needs we are working with STM32 also. Our PCB’s are produced by our trusted partners with some cool ISO certificates. For communication, we love to work with ESP32, SIM800/900, HC-06 and Mikroelektronika Click boards.

Energy consumption

If you know just a little bit about IoT, then you are aware of the fact that IoT devices have to use as little as possible energy. Our modules are ultra-low power and can be battery powered. Of course, we have some modules that need just a little bit more juice but we are constantly improving this solutions. Modules in deep sleep require around 0.26uA and with only small battery modules can work for 90 days in deep sleep mode. It’s pretty important to mention that most of the time IoT modules are sleeping or deep sleeping to keep the battery life.

energy modules
cloud for iot

Server-side and Cloud

Now it gets interesting. IoT modules can be ‘offline’ (at least relatively) and communicate with one another. IoT modules are fulfilling their purpose when they are connected to the internet. For this purpose we are using Google Cloud Platform, that’s the place where our instances are running. Mostly we use our own API based on Laravel framework and HTTPS to transfer simple data in encrypted jSON format. We have a few instances running multiple backends and microservices for different products, we are using NGINX web server to handle all the requests. Of course, we are open to other platforms, like AWS and we are looking forward to creating new instances in their Cloud space.