How does your device get into the Internet of Things easily? The Solcept IoT Platform

Modern devices are supposed to be connected to the IoT (Internet of Things), to the cloud. On the one hand to centrally query sensor data and operating states allowing for e.g.  remote service, planning of maintenance and planned refilling of consumables. On the other hand, the devices should also be configured, controlled and maintained locally with a smartphone or tablet.

Many of these devices contain a controller which is deeply embedded, i.e. consists of printed circuit boards and not of off-the-shelf control components. The effort to implement all IoT-functions and especially the IoT-interfaces can be considerable. This is especially true since these controls are usually very resource-limited (cost, energy consumption/cooling, space, processing power...).

Since the interfaces and the basic functions are the same for almost all applications and customers, we have developed a platform that greatly shortens the development of IoT functionality.  It is not intended to be a "one size fits all" solution, but it is so flexible that it can be adapted with little effort for many "deeply embedded" IoT and M2M (Machine-To-Machine communication) tasks.

We have developed this platform in the context of a concrete customer project with specific sensors, actuators and functions. However, the IoT platform capabilities in hardware and software are encapsulated in such a way that they can easily be transferred to other projects, be it completely or only a part of the functions.

The functionality of the IoT platform includes (see also above drawing: dark part)

  • Communication with the Internet/ the cloud:

    • on the road and outdoors via cellular mobile
    • in closed buildings via Wireless LAN

  • Communication with the local operator

    • for data: Bluetooth
    • for identification/security: NFC

  • Location by satellite navigation

The non-functional requirements that the platform fulfills are also important. These are often the larger limitation than the functional aspects:

  • Data security (identification/encryption)

    • built-in hardware secure element (Root of Trust)
    • secure processor/ system on chip

  • Power supply

    • Lithium batteries (industrial temperature range -30..85°C)
    • wireless charging
    • low power for long service life and easy cooling (especially the communication modules can have a significant power consumption and corresponding cooling requirements)

  • Secure software updates via the Internet, secure boot of the controller
  • Protcols:

    • MQTT (Message Queuing Telemetry Transport)/ AMQP (Advanced Message Queuing Protocol)
    • CoAP (Constrained Application Protocol)

The specific part for the customer's application we have implemented based on this platform. This custom part consists of software and hardware in the embedded system plus of the applications for the cloud, the PC and the mobile. Since the customer gets the sources and schematics of the whole project, there are no dependencies, no "vendor lock-in".

Project Scope

Expertise and Technologies

The platform is based on these technologies and competencies:

Contact us for more information!

These References might Interest You

Internet of Things for Piggyback Transport

How did we adapt the back-end of a telematics solution from road to rail for Ralpin?

Ground Station for Unmanned Aircraft

How did we do it to develop a stable software for planning and visualization, fast?

Complex Software - Simple Coffee Brewing

How did we develop a complex control system at low unit cost for a Franke professional coffee machine?

Let us discuss your idea/ your project