CCS/TM4C123GH6PM: Figured it out

Josh Ingham said:

it seems that I am able to communicate with the sensor using I2C.       When it comes to reading xyz values I just get zero values.

It would prove more helpful if poster would describe,  "How & Why he (seems able) to communicate - via I2C."      (those important facts - omitted.)

"KISS" has been kicked - hard & far - to the curb.    Floats, interrupts, complex sensor, and UARTprintf (in abundance) all serve to,  "Divert from the basic I2C Communication Task" - do they not?      Is this advised?

External pull-up resistors often serve to assist I2C operation - as does a "Vastly Narrowed Focus" - upon the central task.    (which appears here,  "Real I2C Communication.")

Starting w/so complex an I2C device - rather than a low-capacity, I2C based EEProm - is another violation of  "KISS."       Might it (ever) be acknowledged that  "sensor library"  encourages (near) total "Cut/Paste" - kicking both "KISS" and necessary experimentation (which builds understanding) far to the curb...    Are poster's "failed results" - by any means - unexpected?

yes there is activity. Everything looks correct according to datasheet to receive multiple bytes ( MSB of SUB address is set to 1 for auto increment). But when it comes to reading the bytes from the specified register it returns zeroes as can be seen in the pictures below.