update readme.md

This commit is contained in:
rob tillaart 2022-06-12 17:18:20 +02:00
parent 77a71fd646
commit 314a071f28

View File

@ -28,17 +28,46 @@ This is done to minimize interference with the communication of other devices.
The reset clock speed can be changed with **setI2CResetSpeed()** e.g. to 200 or 400 KHz.
## Version problem?
## Version 118 problems
The library can request the version with **getSensorVersion()**.
My devices all report version 117 and this version is used to develop / test this library.
There are devices reported with version 118 which only support the **PPB** and not the **ugM3** mode.
There are devices reported with version 118 which behave differently.
### ugM3 not supported
See - https://github.com/RobTillaart/AGS02MA/issues/11
The version 118 seems only to support the **PPB** and not the **ugM3** mode.
It is unclear if this is an incident, bug or a structural change in the firmware.
So if you encounter problems with setting the mode, let me know.
Also if you have a working device, not being version 117 or 118 let me know too.
If you encounter similar problems with setting the mode (any version), please let me know.
That will help indicating if this is a "structural change" or incident.
See also - https://github.com/RobTillaart/AGS02MA/issues/11
### Calibrate problem!
See - https://github.com/RobTillaart/AGS02MA/issues/13
In this issue a problem is reported with a version 118 sensor.
The problem exposed itself after running the calibration sketch (command).
The problem has been confirmed by a 2nd version 118 sensor.
Additional calibration runs did not fix the problem.
Version 117 seem to have no problems with calibration.
**Advice**: do **NOT** calibrate a version 118.
Note: the version 0.2.0 determines the version in the calibration function so
it won't calibrate any non 117 version.
### Please report your experiences.
If you have a AGS20MA device, version 117 or 118 or other,
please let me know your experiences
with the sensor and this (or other) library.
## Interface