-
I am working with the following MCP9600 I2C THERMOCOUPLE AMP which has a default address of 0x65 and the ability to set to 0x67. I am wondering why the following was added to restrict the address range for this module? I have commented out the check to use the address I need and it appears everything works fine. I am not sure what I should do to move forward. I am willing to open a new PR request, but not sure how to handle my needs. Comment our the code or create a new module explicit for the MCP9600. esp-idf-lib/components/mcp960x/mcp960x.c Line 175 in a43fa64 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi! |
Beta Was this translation helpful? Give feedback.
-
Hi!,
Yes. As I mentioned I have the following MCP9600 I2C THERMOCOUPLE AMP
<https://www.digikey.com/en/products/detail/4101/1528-4101-ND/10245127?itemSeq=324782003>
it
allows for addresses (0x65 and 0x67). it would be great to add those
…On Mon, Apr 11, 2022 at 7:43 PM Ruslan V. Uss ***@***.***> wrote:
Hi!
This is common practice for all drivers in this library. This approach
allows to identify common errors in programs associated with incorrect
device addresses.
If you find that the driver does not support a valid address, please let
me know this address and I will add it to the condition.
—
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFFMWJXRC46N5COM2WYS3VETBKPANCNFSM5TBBIXWA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Fixed in ccdacdd. |
Beta Was this translation helpful? Give feedback.
Fixed in ccdacdd.
Thank you!