@dblessing wrote:
At a quick glance, I don’t see why One-Wire stuff wouldn’t work. It would be nice to know what I2C address those sensors use. Currently, with the OS board and the LCD my I2C address table looks like this:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
The above is found my running `i2cdetect -y 1` for the Rev2 Pi. Those addresses translate to 0x20, 0x48 and 0x68. The 0x20 is the LCD and the 0x48 and 0x68 are the OSPi. Don’t quote me.
Looks like Maxim/DS provides a 1-Wire/I2C bridge chip called the DS2482 that could handle the interfacing between I2C and the 1-Wire bus.
http://www.farnell.com/datasheets/1675710.pdf
According to the data sheet: “The I2C slave address assignment is controlled by two binary address inputs, resolving potential conflicts with other I2C slave devices in the system.” Given the large number of 1-Wire devices (thermocouples, thermistors, switches, ADC, pressure transducers, etc), this could be a viable way to interface with the “outside world” using the RPi mounted onto an OSPi. The downside is that 1-Wire stuff is relatively slow, but fine for most applications that would be hosted by an RPi.