You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, during setup of MATEK F405 WSE and I have run in to some kind of problem.
I wanted to add temperature sensors LM75 which by default talk with I2C2
and I wanted to use I2C1 since it had free pins on the FC.
Finally I modified the INAV firmware and after rebuild it works fine.
After all this I started to think about long term solution and I would like to ask:
why temp. sensors are using I2C2 since I2C2 is use by (not counting temp. sensor): compass, Pitot sensor, rangefinder
and I2C1 is used by: barometer, possibly LCD which is IMHO more trouble then it is worth. So it seems that I2C1 is less crowded than I2C2 ?
is it possible to choose by CLI command which I2C should be used for temp. sensors ?
This discussion was converted from issue #9017 on May 01, 2023 14:21.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Recently, during setup of MATEK F405 WSE and I have run in to some kind of problem.
I wanted to add temperature sensors LM75 which by default talk with I2C2
and I wanted to use I2C1 since it had free pins on the FC.
Finally I modified the INAV firmware and after rebuild it works fine.
After all this I started to think about long term solution and I would like to ask:
and I2C1 is used by: barometer, possibly LCD which is IMHO more trouble then it is worth. So it seems that I2C1 is less crowded than I2C2 ?
Beta Was this translation helpful? Give feedback.
All reactions