Platforms

CoE@JP

This CoE is focused on the IEEE 1451 and concerning the IES standard using MQTT, especially IEEE P21451-1-6. MQTT is a standard of OASIS. OASIS is a community that offers the path to standardization and de jure approval for reference in international policy and procurement. Ahead to organizing the working group for this standard of Smart Transducer Interface for Sensors, Actuators, and Devices - Message Queue Telemetry Transport (MQTT) for Networked Device Communication, OASIS technical committee granted the permission of the use of MQTTv3 and v5 as the activities and the objectives of this standard. MQTT uses TCP/IP and provides simple and lightweight communication. The main use case of MQTT is to connect small sensors and actuators, such as IoT devices, with server applications. MQTT is based on the publish-subscribe communication paradigm, whereas general communication protocols are based on the response-request communication paradigm. Here, a transducer means both a sensor and an actuator. The CoE supports the IEEE 1451 and concerning standard and working group activities.

Platform Architecture

This CoE offers an experimental environment and setups, observing different configurations, with the required characteristics to integrate the device under test and evaluate its behavior. This CoE has supported MQTTv5 broker and the environment from its early developing stage, and continuously supports the penetration of new MQTTv5 features for updating the functions, usability, and designability of new standards. The following system is available at CoE@JP, and everyone can access the broker to connect the given IoT devices. It is usable to check the connectivity and interoperability with IEEE P21451-1-6 and the concerning standards. We prepared the following two different systems.

System #1: Intel Architecture-based Configuration

System #1: Intel Architecture-based Configuration

System #2: ARM-based Configuration

System #2: ARM-based ConfigurationAvailable NCAPs

Two versions of NCAPs are available.

  • Raspberry PI runs an NCAP application that support TIMs wireless connect through Bluetooth rfcomm mode.
  • We used Raspberry Pi 3 B/B+ / Raspberry Pi 4
    • NOOBS / Raspberry-Pi OS + bluepy + alps_extension
    • Raspberry Pi 3 Model B use 1.2 GHz 64-bit quad core ARM Cortex-A53 processor, on-board 802.11n Wi-Fi, Bluetooth and USB boot capabilities
    • Raspberry Pi 3 Model B+ has a faster 1.4 GHz processor and a three-times faster gigabit Ethernet (throughput limited to ca. 300 Mbit/s by the internal USB 2.0 connection) or 2.4 / 5 GHz dual-band 802.11ac Wi-Fi (100 Mbit/s. Power over Ethernet (PoE) (with the add-on PoE HAT), USB boot and network boot (an SD card is no longer required) are available.

ARM host

  • Stick PC of Intel architecture runs an NCAP application.
    • Intel Compute Stick (CORE m3 model)
    • Soldered-down BGA 14 nm Technology, 64GB eMMC, 4GB LPDDR3-1866 memory, MicroSDXC with UHS-I support, USB3.0, Intel Wireless-AC 8260 + Bluetooth 4.2 (Not compatible to BLE) are available.
    • Intel VT-x, PTT, AES instruction sets are available.
    • We used Bluetooth USB Adapter LBT-UAN05C2 (Bluetooth 4.0) for supporting BLE. Integrated Bluetooth is not capable of stable BLE modules management

Intel host

All NCAP applications were designed by using Python programming language.

Available TIMs

Two versions of TIM are available.

  • Raspberry Pi runs a wired/wireless TIM that can connect to the NCAP through WiFi/Bluetooth rfcomm. It connects with the BLE IoT modules through BLE.
  • Stick PC of Intel architecture runs wireless TIM with NCAP application. These applications are separated and are executed on the same machine. The TIM application enables to connect with BLE IoT modules via BLE dongle for its stable operation.

All NCAP applications were designed by using Python programming language for integrating TEDS management and broadcasting functions and connecting with IoT devices using original protocols.

 Available publishing/subscribing platform

  • Intel NUC server runs a MQTT broker (mosquitto) with wired/wireless communication media. It also connects with the Internet.

 Available sensor nodes

  • ALPS IoT Sensor (BLE)
    • Power 2.35-3.30V 7mA(Peak), Bluetooth 4.1(BLE)
    • 6D Acceleration Sensor (-2G – 2G extendable)
    • Presser Sensor (300-1100hPa, 0.013hPa/LSB)
    • Temperature (-20 - +85 C, 0.02 C/LSB)
    • Humidity (0 – 100%, 0.016%/LSB)
    • UV (0 - 20.48mW/cm2)
    • Illuminance (0 – 81900Lx, 20Lx/LSB)

ALPS IoT Sensor

  • Node MCU
    • NodeMCU development board is a powerful solution to program microcontrollers and be part of the Internet of Things (IoT). The NodeMCU development board, based on ESP8266EX, is SoC module with a microcontroller, integrated Wi-Fi receiver, and transmitter.
    • Low cost, Simple, and Programmable device. Design by using Arduino IDE with open-source original extension.
    • Wi-Fi enabled
    • Deep sleep power <10uA, Power down leakage current < 5uA and Standby power consumption of < 1.0mW
    • Wake up and transmit packets in < 2ms
    • Build-in json, file, timer, pwm, i2c, spi, 1-wire, net, mqtt, coap, gpio, wifi, adc, uart and system api.

Node MCU

  • Intel Neural Compute Stick 2
    • This Neural Compute Stick accelerate Deep Neural Network (DNN) applications
    • Hardware: Intel® Movidius™ Myriad™ X VPU
    • Software: Intel® Distribution of OpenVINO toolkit
    • Neural Compute Engine: SHAVE Cores (16 powerful processing cores)

Movidius VPUMachine Learning Application Accelerator