The final implementation will only use the M5HAL, but it has also been made to work on a TwoWire-based, so that development and testing can proceed without reliance on the M5HAL.

For development and checking convenience, including those that are inherently separate repositories

New repositories to be split in the future.

lib/M5Utitliy
M5UnitUnified, M5UnitComponent, M5HAL, and other depends it.
lib/M5UnitComponent
M5UnitUnified depends it.
lib/M5PaHub
For PaHub
lib/M5HAL
M5UnitComponent depends it.

Add to existing libraries in the future

lib/M5Unit-ENV
UnitComponent for SCD4x, SHT30, QMP6988...

Implemented

Body \ Unit	SCD40	SHT30	QMP6988
Core	test,example	test,example	test,example
Core2	test,example	test,example	test,example
Core3	test,example	test,example	test,example
StampS3	test,example	test,example	test,example
AtomS3	test,example	test,example	test,example
NanoC6	test,example	test,example	test,example

How to try examples (PlatformIO only)

If you want to try it on other devices, edit the ini accordingly.
lib Once the repositories for each of the libraries below are in place, they can be compiled by ArduinoIDE.

Note that the M5HAL experimental version is not up-to-date and may have glitches

[env:example_SCD40_foo]

examples/SCD4x/SCD4x.cpp

#define USING_PAHUB (2) // Connection channel number for use via PaHub.
#define USING_M5HAL  // Using M5HAL is defined

Switch between TwoWire and M5HAL versions with and without USING_M5HAL defines
Switch between directly connected and via PaHub versions with and without USING_PAHUB defines
Connecting the SCD40 to the USING_PAHUB numbered channel.

[env:example_ENV3_foo]

examples/UnitENV_III/UnitENV_III.cpp

#define USING_SINGLE_SHOT // Using single shot measurement If defined
#define USING_ENV3 // Using combined unit if defined

Switch between single instance versions of each chip and Env3 instance versions
Switch between periodic and voluntary measurements

How to try UnitTest (PlatformIO only)

This should be done with a direct connection, not via the Hub.

env:test_foo
[Advanced]_ - [Test]

Choose target unit

;test_filter= embedded/test_sht3x
;test_filter= embedded/test_qmp6988
test_filter= embedded/test_scd4x

M5UnitComponent

Basically, a unit is created for each chip. (UnitSHT30, UnitQMP6988...)
When multiple chips are mounted, as in the case of ENVIII, it can be expressed as a form in which ENVIII holds each chip.
See also unit_ENV3.hpp

Should I create a unit with a product name, even if it is a single chip like a CO2 unit?

API Documentation

doxygen and pcregrep required

bash docs/doxy.sh
open docs/html/index.html

Running the command with the respective current will output the respective document

M5UnitUnified
lib/M5UnitComponent
lib/M5Utility
lib/M5Unit-ENV

By adding to existing libraries, the reference manual can be developed from the source.
It would be useful to use GitHub Action to automatically generate documentation and publish it on GitHub Pages or m5doc upon master release.

UnitTest

Create unit tests by googletest that are native (if possible) and embedded in each units.
This is necessary to check operation, isolate problems when they occur and prevent regressions.

The M5UnitUnified test checks for collisions between the unique IDs assigned to the units.
Unit-specific tests will be placed in the respective library repositories. (Some working test are currently placed in examples for development convenience. Will be moved before release).

Examples

The example of the UnitUnified itself depends on the connecting unit and will be added to the example in each unit's library.
(Some working examples are currently placed in examples for development convenience. Will be moved before release).

Questions

https://github.com/m5stack/M5Template-C-CPP/

.clang-format is much older.
There are items that have been changed in the current version, etc.
Prerequisite version is 13?
What about updating to the latest settings?
The number of column digits is 80, can it be made larger?

Overview

SKU:xxx

Description of the product

Document & Datasheet

Required Libraries:

Adafruit_BMP280_Library

License

Product Name- MIT

Remaining steps(Editorial Staff Look,After following the steps, remember to delete all the content below)

Change clang format check path.
Add License content to LICENSE.
Change link on line 78 of bug-report.yml.

Example
# M5Unit-ENV

## Overview

### SKU:U001 & U001-B & U001-C

Contains M5Stack-**UNIT ENV** series related case programs.ENV is an environmental sensor with integrated SHT30 and QMP6988 internally to detect temperature, humidity, and atmospheric pressure data.

## Related Link

- [Document & Datasheet](https://docs.m5stack.com/en/unit/envIII)

## Required Libraries:

- [Adafruit_BMP280_Library](https://github.com/adafruit/Adafruit_BMP280_Library)

## License

- [M5Unit-ENV - MIT](LICENSE)