An EEMBC Benchmark 

IoT-Connect FAQs

Will EEMBC implement a 'very' sleepy node profile?

A very sleepy node may fit the profile of an energy harvesting device. We are not planning to support such nodes. There is nothing inherently wrong with the approach even for those types of nodes, but implementation wise it would be a different implementation. An energy harvesting device will not consume any energy off of the energy monitor, and as such will require a different way to measure the energy consumed.

With mesh networking on the horizon for Bluetooth, is EEMBC planning on including Bluetooth Mesh in its IoT Benchmark suite?

For the first release, the IoT Connect Benchmark working group is currently working on incorporating support for Bluetooth Smart (BLE). For subsequent releases, we are discussing Thread mesh networking. Support for these protocols will help define how mesh endnodes are benchmarked. Once Bluetooth Mesh is more mature, and public, our working group will discuss adding it to the IoT Connect benchmark as a new profile.

What types of wireless connectivity are supported by the IoT Connect Benchmark? Is wifi on the list?

The working group is currently defining benchmark profiles for Bluetooth Smart (not Bluetooth Mesh at this time). For the subsequent version, we are considering Wifi, Thread, and LoRA.

For the IoTMark-BLE, does EEMBC specify an antenna, transmit power, or other transmission details?

Yes, the certification transmit power is set to 0 dBm. We realize some boards do not support this, but this is defined as the most common baseline for comparison by a number of contributors to the benchmark. During certification, the device under test must provide an RF cable connector in order to verify the transmit power with a spectrum analyzer.