Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

In IoT World, we are starting from analog world and connecting to digital cloud and hence multiple layers play the role in the middle.

In general, an IoT application (solution) can be divided into three segments:

  1. The sensors and actuators
  2. The micro-controllers (MCUs)
  3. The application

 

1. Sensors or Actuators

    Sensors and actuators are the physical touch points to the physical world.  They come in two categories - Analog and Digital. Analog sensors need electronics to convert analog signals to digital output. Digital Sensors have this electronics as part of the sensor.

https://learn.sparkfun.com/tutorials/analog-vs-digital

2. MCUs

     Data coming directly from sensors and actuators

 

Sensors and Actuators can't be connected as it is to high end computers, who only provide serial interfaces like Bluetooth, USB, DB9, etc. There is intermediary electronics required to take analog or digital signals, compute the information and forward it upstream or vice-versa. Computed information from sensor is passed on a communication channel or forward the message from communication channel to actuator by using embedded software on the MCU.

https://www.sparkfun.com/tutorials/93

Analog Sensors can connect to analog pins and digital sensors are connected to digital pins. Northbound of MCU depends on the comm support from the MCU. It can be wired serial or wireless serial. Newer generation of MCU's may directly support IP protocols.

Gateway

     Most of the MCU's support local protocols and hence any connected solution needs a gateway to take local protocols and expose the interfaces on IP based protocols. Here TQL Engine plays the role and abstracts all sensors and actuators connected through MCU's and/or devices connected on wireless or wired protocols and maps into local domain - like agriculture, parking, traffic, etc.

     In some situations, instead of gateway, there may be only appliance where TQLEngine runs and integrates with all connected (wired or unwired) devices.

Cloud

     Cloud can be private (in enterprise datacenter) or public (AWS). TQLEngine runs in the cloud to aggregate all edge TQLEngines and directly connected devices (through IP stack).

Refer to a topology picture for the Greenhouse tutorial (to be created later) TQLDOC-9 - Getting issue details... STATUS

 

  • No labels