• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 28 subscribers
  • Views 338 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Sensor Hub Booster pack for EK-TM4C1294NCPDT

Dhruv Bhardwaj1
Intellectual 420 points

Hello,

I am working on EK-TM4C1294NCPDT and I am using Sensor Hub Booster pack to collect the sensor values. I want to use all of the sensors available on booster pack in my program. But these sensors have been developed by different companies I guess and each one has different libraries, but they all are using I2C7 port for reading data from their sensors. So my question is: Is it possible to read all sensor values from Booster pack in one program? Because I tried to use other port of I2C but it gave me absurd values.

Thanks!

  • 0
    Guru 47900 points

    Dhruv Bhardwaj1 said:
    Is it possible to read all sensor values from Booster pack in one program? Because I tried to use other port of I2C but it gave me absurd values.

    Absurd values are indeed troubling - yet also troubling are posts where (likely) critical information is missing/withheld.

    Read all values in one program - might this depend upon your program's objective - and any/all interconnects in play between the MCU and remote sensors?  Speed of execution and recovery from any/all I2C "hangs" may also prove important - yet all are absent - your writing.

    You moved from I2C7 but fail to explain why.  Will a 2nd I2C instantiation of your MCU simplify or shorten your program?  Predictably in doing so - the necessary pull-up resistors - resident upon I2C7 - may be lacking upon another I2C port - and result in those "absurd" values.

    You provide no usable input with regard to (any) success using I2C7.  Did you communicate with one, several, most or even all of the I2C slaves?  It's troubling that you moved from the designer's chosen port - w/out providing any justification for such movement...

    Did you "break" any/all connections between I2C7 and I2Cx prior to attempting your new I2C communication?  Did you properly/completely set-up and configure Port I2Cx?   And - beyond your report of (absurd) values - what were those values?  Did the slave(s) Ack?  Did you monitor both SDA & SCL for activity - proper signal levels - and signal edges?  Did you attempt communication with multiple slaves - did all such communication fail?  (Failing to provide this level of detail may better qualify as (your word) "absurd.")

    Divide and conquer often proves effective in programming/design - but most all such success stems from a good plan - and well executed implementation.  And that seems less than fully evident - here...

    Today has seen a rash of poorly conceived posts - "attention to detail" - consideration for hapless "helpers" - appears not too "high" in poster priority...  (Me, me, me - right now - in detail - after all it's URGENT!)  (on what planet?)