<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LIS2DH integration I2C</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33386/lis2dh-integration-i2c</link><description>Hi, 
 Not directly related to Nordic, but I as many people are doing the same I figured it&amp;#39;s fine. 
 is there any reason why this would not work? assuming the I2C is already working with another sensor and assuming no HW bug 
 LI2DH datasheet command</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 13 Apr 2018 18:45:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33386/lis2dh-integration-i2c" /><item><title>RE: LIS2DH integration I2C</title><link>https://devzone.nordicsemi.com/thread/128305?ContentTypeID=1</link><pubDate>Fri, 13 Apr 2018 18:45:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92c1b23a-a7b3-47a1-95a1-867b5a3a8ed4</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;Yes; it will be confused. try swapping the expected response for the command request :-)&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// Device identification register.
#define WHO_AM_I                        0x0F
#define I_AM_LIS3DH                     0x33
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>