It takes only a few minutes …
… to visualize your device temperature on a web frontend.
All in ONE IoT Ecosphere
Cellular IoT for industrial grade solutions has never been easier. One revolutionary ecosphere for serious development results. Simple workflows and 100% online development result in significant resource reduction for lifecycle management.
… to visualize your device temperature on a web frontend.
// ---
// applicaion main loop triggered every second
// ---
#callback appLoop()
{
new sht31[DDE_sht31]; // Initialize the data structure
SHT3x_read(sht3x, sht31.temp, sht31.rh); // Read the temperature and humidity
DDE_sht31_write(0, sht31); // and forward them to the cloud
}
Microtronics ONE is a set of fully integrated tools and examples to get you started easily and accompany you throughout your whole product journey, from initial ideation to operating it at scale. Microtronics ONE allows you to focus on the business objectives, silently tackling obstacles to great extent, such as customizing, lifecycle and permission management, security, performance and connectivity as a whole. Interoperable and from one single vendor.
Microtronics ONE is a unified foundation to build flexible IoT use cases upon. It is more than a standard, a protocol, a messaging systems, a device management platform. In a way it is all of that, readily integrated. On first contact, Microtronics ONE is best experienced by stepping through the quick start guide and demo example. Try out the starter kit right away, or take a look at the documentation.
The application framework is built with reusable libraries and lifecycle management in mind. This unlocks ground-breaking resource efficiency during the design and lifecycle management of the product.
Both Microtronics itself and the technology have continued to evolve since 2006. We have recently added a product to our portfolio that is specifically aimed at developers. We build cellular industrial-grade IoT solutions since before the term was coined, with tens of thousands of active devices in the field in this very moment. As a partner, Microtronics is committed to sustainable development and reliable operations, as underlined with system level certifications according to ISO 9001, 14001, 27001. Microtronics is 100% IoT.
The technology stack is direction-agnostic. You can upload data from devices to the cloud or do the exact opposite. Access is one area of application where this is used successfully, for various remote gate control scenarios, to give an example.
For every mobile application cellular connectivity is the way to go. However, in many fixed installations cellular connectivity allows simple plug and play installation procedures. The simplicity in installing or activating consumer or professional equipment is an important reason why many applications integrate cellular connectivity into their product. Additionally keep the connectivity infrastructure separated from the local corporate network is in many cases the most efficient way to go.
While we cannot definitely answer this for you, from experience: chances are, yes. More generally put, cellular connectivity is your go-to-option if you need to reliably connect from a remote location with no wired network infrastructure, perhaps without a power source nearby either, eventually from locations all across the globe, to transmit high resolution data.
That said, cellular connectivity does have its disturbances and mobile network operators (MNOs) do not tend to commit to availability numbers either. Even though connectivity is included as such, the service quality of Microtronics ONE is reliant on MNO delivery with regards to the availability of cellular networks. . Yet Microtronics ONE has several resilience mechanisms built in, such as local buffering and auto-reconnects, to overcome temporary outages without losing precious data points and, more often than not, without anyone noticing.
Additionally , cellular connectivity in Microtronics ONE is solely depending on an existing uplink, i.e. an available mobile network. Data protection to ensure confidentiality and authenticity, compression, time-oriented, order-preserving transmission etc. is all independently ensured within the protocol.
No. Microtronics does not provide mobile network infrastructure or services on its own. Microtronics is partnered with MNOs, who in turn have global roaming agreements with a large network of MNOs.
Connectivity plays an integral role in every IoT use case. Yet it is a tedious technical process that requires alignment among several vendors to reliably set up a communications channel between edge devices and the central infrastructure. Microtronics strives to lower the IoT-tech-barrier as much as possible, so you can delve into the business application right off the bat. We believe that to be a major simplification for customers, compared to engaging with different vendors to get a reliably working technical baseline established.
Most likely, yes. We have successfully put global use cases into operation, in metropolitan and rural areas as well as within buildings. That said, there may be blind spots and it varies in how exactly it works in terms of the locally supported technology (and hence bandwidth, ability to penetrate walls, etc.). We will dive into the nitty gritty details for your specific requirements. Do not hesitate to get in touch with questions.
Regarding personal data, Microtronics is fully committed to GDPR compliance, and you are free to execute your therein granted rights any time. Further, Microtronics operates its data centers in Austria, within the European Union and therefore within GDPR jurisdiction.
Microtronics ONE is not an advertising platform, there is no profiling in the GDPR sense and removed accounts will have their data reliably deleted from our services.
Regarding intellectual property, it is you as the creator who remains in sole control over design and implementation of any custom application that is developed in the provided IDE, within the Microtronics ONE ecosphere. Microtronics retains the right to block or remove content if it violates terms of use, dual use or other regulatory constraints.
You choose with whom to share it with and how to license or monetize it. Microtronics grants the use of the provided tools, infrastructure, programming libraries and documentation, within the ecosystem, for as long as an account exists.
Consequently, you can choose to make your released app available publicly for others or keep it private.
Regarding operational integrity, Microtronics is committed to regular updates regarding both the cloud and device software stacks. Cloud updates are rolled out at the discretion of Microtronics, with accompanying information. Device firmware is announced and provided, with the installation time being at the user’s discretion. Both types of software updates retain data integrity. Any change in settings that may affect data integrity is to be done by you directly and is blocked for internal support unless your consent is given. Management of app updates, as released from the provided Microtronics Studio IDE, is solely at the user’s discretion.
Microtronics devices can be trimmed as needed with a tailored scripting language (the scripting language is based on Pawn by CompuPhase) and simple markup to describe data structures. Think of it as simplified C. Syntactically similar, yet typeless and without structures, using references while refraining from pointers. Easily adopted by C programmers. Compiled into intermediate language, optimized for efficient execution on an isolated abstract virtual machine on constrained devices.
Both Yes and No, depending on what you need to achieve. At its heart, Microtronics ONE is centered around a battle-proven, proprietary protocol we call UTO (for Universal Transferable Object). UTO is three things at once:
That said, there is not much direct contact with UTO when using Microtronics ONE, as it is all abstracted away.
Therefore:
Yes, within the Microtronics ONE ecosphere you can simply share projects on an individual user basis. Users who have access to a project can collaborate simultaneously and remotely.
You. Assisted with many inherent aids to avoid mistakes.
For example:
Microtronics ONE runs device scripts in a sandboxed environment, which prevents custom code from wreaking havoc in the underlying device memory or microcontroller registers. Consequently, devices will remain recoverable (custom code cannot brick them) and retain memory integrity. As with any other app store model, however, it is you who needs to check whether the code in question does exactly what’s needed, when needed.
Microtronics ONE unifies cloud features and service delivery, connectivity and mobile data volume, maintenance of device firmware and tenancy-aspects into one billing unit: data operations. Data operations enable a fair, usage-oriented consumption model that scales with the extent one uses the product.
A data operation is one action upon a usage data point. That is, data relevant for your use case. Transferring a single data point to the cloud represents a data operation. Further combination of data points are data operations. Reading via the API, user- or other interfaces consumes data operations as well.
Data operations are preloaded in blocks and then withdrawn per your use case. You can control how resource-intensive your application is, by controlling sensitivity, measurement intervals, caching strategies, etc., thus reduce load on our systems and hence ensure optimized, cost-effective operations. Microtronics ONE equips you with indicators, a historical view and a starting balance to help predicting monthly consumption.
To interactively experience Microtronics ONE apart from delving through screens of documentation, you need a starter kit. The starter kit is a piece of hardware capable of demonstrating
It comes with a starting balance of data operations (see question above), for a hassle-free first evaluation of Microtronics ONE. We can write stacks of papers and you still won’t get the idea as if just trying it out. Yet we want you to know what you get into before committing to bigger packages. Hence the preferred first step in the Microtronics ONE journey is a bit of exploration with a starter kit.
From there, you can proceed in your own pace. Prolong evaluation, restock on data operations, abandon it without having to untie a hidden subscription of sorts, or progress into more elaborate prototyping with your own hard- and software ideas.
Feel free to use the chat or the contact form for your further questions.
Microtronics Engineering GmbH
Hauptstrasse 7
3244 Ruprechtshofen
Austria
Microtronics Engineering GmbH
Hauptstrasse 7
3244 Ruprechtshofen
Austria
