<div dir="ltr"><div><div><div><div><div>Bit more digging re ic switch:<br></div>My understanding is that if we got one of these:<br><a href="http://uk.farnell.com/roth-elektronik/re933-03/adaptor-smd-tssop-16-0-65mm/dp/1426182">http://uk.farnell.com/roth-elektronik/re933-03/adaptor-smd-tssop-16-0-65mm/dp/1426182</a><br>
</div>and one of these:<br><a href="http://uk.farnell.com/nxp/pca9546apw/ic-switch-4ch-i2c-16tssop/dp/2212120">http://uk.farnell.com/nxp/pca9546apw/ic-switch-4ch-i2c-16tssop/dp/2212120</a><br></div>we should in theory be able to run both sensors off the same pins?<br>
</div>BUT - would the current code you wrote function better/easier if the sensors were run from 2 separate sets of pins - ie how to parse the info from one patch sounds tricky and presume much simpler with 2 [netreceive] objects attached to 2 C files?<br>
<br></div>J<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 April 2013 09:42, Julian Brooks <span dir="ltr"><<a href="mailto:jbeezez@gmail.com" target="_blank">jbeezez@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Hey Martin / all,<br><br></div>Omron tech support finally got back to me re the address issue, this is what they had to say:<br>
<br>"<font><tt></tt></font><font><tt>D6T sensor can not change the address.</tt></font> <br>
<font><tt>When you connect multiple sensors we recommend that you use the IC switching.</tt></font>
<br>
<font><tt>Please refer to the below document.</tt></font> <br>
<font><tt> <a href="http://media.digikey.com/pdf/Data%20Sheets/Omron%20PDFs/D6T44L_8L_Appl_Note.pdf" target="_blank">http://media.digikey.com/pdf/Data%20Sheets/Omron%20PDFs/D6T44L_8L_Appl_Note.pdf</a>
</tt></font>"<br><br><br></div>I've been through the spec sheet several times and don't see anything (admittedly not sure exactly what I'm looking for though) that relates to IC switching.<br><br></div>We've still got 2 of these doing nothing currently if they could be brought into action:<br>
<a href="http://adafruit.com/products/757" target="_blank">http://adafruit.com/products/757</a><br><br></div>Or people on the RPi forum seem to have got the 2nd i2c pins going but that seems to be for rev.2 boards only (I think - have posted a question on the thread to ask).<br>
<br></div>Also asked tech support about the PEC errors but no response to that one.<br><br></div>I've noticed that the PEC doesn't trigger errors all the time so am wondering if it's possible to filter the errors out of the data somehow in the C file?<br>
<br></div><div>Still delighted though - the sensors great!<br><br></div><div>Cheers,<br><br>Julian<br></div><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 22 April 2013 00:20, Julian Brooks <span dir="ltr"><<a href="mailto:jbeezez@gmail.com" target="_blank">jbeezez@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Wonder if it's a difference between rev boards on the Pi? <br><br></div><div>I've also built a custom image based on Hexxeh's minimal install which is working great for audio stuff. My Pd patch that wouldn't run without overclocking on a standard Raspian is now working fine on the rev1 256mg board. So I've been adding stuff as and when it comes up to try and keep t is minimal as poss.<br>
</div><div><br></div>I'm also not sure what installed libi2c-dev? Guess I'll have to wait and see what squeals.<br><br></div>Of possible interest is this message when removing the lib with apt-get:<br><div><div>
The following packages will be REMOVED:<br>
libi2c-dev<br>0 upgraded, 0 newly installed, 1 to remove and 11 not upgraded.<br>After this operation, 19.5 kB disk space will be freed.<br>Do you want to continue [Y/n]? y<br>(Reading database ... 33610 files and directories currently installed.)<br>
Removing libi2c-dev ...<br>Removing 'diversion of /usr/include/linux/i2c-dev.h to /usr/include/linux/i2c-dev.h.kernel by libi2c-dev'<br><br></div><div>So guess the diversion was messing with the compile for the C code.<br>
<br></div><div>Anyway - code runs and I can compile C files too so all ok so far.<br><br></div><div>Thanks again for everything Martin,<br><br></div><div>Julian<br></div><div><br><br><br></div></div></div><div>
<div><div class="gmail_extra">
<br><br><div class="gmail_quote">On 21 April 2013 06:45, Martin Peach <span dir="ltr"><<a href="mailto:martin.peach@sympatico.ca" target="_blank">martin.peach@sympatico.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 2013-04-20 21:09, Julian Brooks wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Oh and btw<br>
<br>
Still don't know why I can't compile the .c files on the pi with<br>
libi2c-dev installed but I can't. Presuming the compiling is working<br>
for you Martin?<br>
</blockquote>
<br></div>
Yes it works for me. I don't have the same /usr/include/linux/i2c-dev.h as you so no redefinition errors, not sure which package(s) install that file.<span><font color="#888888"><br>
<br>
Martin<br>
<br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>