Skip to content

Commit

Permalink
Merge pull request #4837 from tonhuisman/feature/P047-update-change-a…
Browse files Browse the repository at this point in the history
…ddress-documentation

[P047] Update address-change documentation
  • Loading branch information
TD-er authored Oct 12, 2023
2 parents 925ee8d + 1ebfb8e commit 3b9416d
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/source/Plugin/P047.rst
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,8 @@ The available settings here depend on the build used. At least the **Force Slow

* **I2C Address (Hex)**: The address the device is using. The default I2C address is prefilled, and can be configured to use a different address, see below. As this can be any valid I2C address in range: 0x01..0x7F, it has to be typed here, using a hexadecimal value.

.. note:: If the device doesn't stay enabled after setting the Enabled checkbox, then possibly the address of the sensor is changed from the default. The I2C Scan on the Tools page can be used to detect what I2C device addresses are in use (disconnect other I2C devices to avoid confusion). Possibly, another device-model is listed for this sensor, but that is caused by the feature that it can have any address set that's in the I2C allowed range of 0x00 to 0x7F.

Device Settings
^^^^^^^^^^^^^^^^

Expand All @@ -81,6 +83,8 @@ When selecting the BeFlE sensor, only these **Device Settings** will be availabl

* **Change I2C Addr. to (Hex)**: The new address to be used by the sensor. The change will be applied the next time the task is enabled. The **I2C Address (Hex)** field, above, will be updated with the new value. After the change is applied, **the tasks Settings have to be saved once more to save the new address** as the address to use.

.. note:: The newly set address is permanently stored in the sensor, and can be changed again at a later time if desired.

Data Acquisition
^^^^^^^^^^^^^^^^

Expand Down

0 comments on commit 3b9416d

Please sign in to comment.