November & December 2023

After investments in R&D, Greenspector is proud to release new product about measurement of IoT devices and a new multi-criteria Environmental footprint assessment API …

New features

Test Runner

  • The Test Runner provides tools to measure iot devices. It provides a new GDSL iot for electronic card (like STM32) which describes the actions to make on the device. It can communicate with iot devices using serial port or socket. In charge to manufacturer or other actor to implement GDSL command on the electronic card.

  • During the test, various iot devices can be used and communicate with each other. The Test Runner can launch test on the main electronic card ( the GDSL commands run on the card), and measure the other “slave” devices.

Environmental footprint API

  • The api returned the CO2, surface and water metrics. The API is now transform into a multi-criteria API to take into account ADEME multi-criteria environmental metrics. Greenspector choose to calculate the following metrics …

    "climate-change" // kg CO2-eq "particulate-matter" // disease incidence "acidification" // kg mol H+ "photochemical-ozone" // kg NMVOC-eq "ionising-radiation" // kBq U-235 "abiotic-depletion-elements" // kg Sb-eq "abiotic-depletion-fossil-fuels" // MJ "eco-toxicity" // CTUe

Improvements

Environmental footprint assessment CLI

  • Improve error display by adding a format check for each column in the input Excel file

Environmental footprint API

  • Route /footprints/global was rename to route /footprints/custom

  • Change default network type distributions (model distributions.NetworkTypes) in the swagger. (routes concern are /footprints/custom and /footprints/networks)

  • Delete route /multipleFootprints which was used by Environmental footprint assessment CLI

  • When using brick ‘client usage time’, the input hardwareType which is mandatory has been taken out from the input parameters which contains optional parameters

    client usage time2.png

Fixed bugs

TestRunner, TestBench

Fixes the lack of network rules and small network score when launching benchmark on some url. In fact the test was successful but only a warning was displayed on the test tracking page indicating an error (ERR_HTTP2_PROTOCOL_ERROR or ERR_UNEXPECTED_PROXY_AUTH) so the user could not see this warning and consider the benchmark test as good.

GDSL

Fixes command enableSettings / disableSettings for android 11+ and for tablet in landscape mode

Documentation