one wire bus support

[Mark paul]

I want to ask, whether snapsethe company intends to support the one-wire bus? We have a lot of clients have the need, in the storage management industry, as well as other areas of temperature measurement, one-wire bus is quite an advantage.

[kbanks]

We have no plans at present to add support (SNAPpy built-ins) for "1 wire bus", since we already support serial IO, parallel IO, SPI, I2C, and CBUS.

Depending on the speed requirements (I have not looked at 1-wire bus), you may be able to control such a device using a SNAPpy script (setPinDir(), readPin(), writePin()).

If the timing requirements of the device preclude the use of SNAPpy, take a look at the "Extending SNAPpy with C Functions" application note that was posted last week. You might be able to interface to a "1 wire" device using similar techniques.

As always, customers who have a specific need for something not already in the existing product can contact our Custom Solutions Group.

[mgenti]

Also there are some I2C to one-wire devices:
See this thread

[RFAndy]

Maxim IC I2C to 1 Wire bridge - DS2482.
The RF Engine should be able to read this I2C device?

It takes about 750 ms to read 1 Wire bus devices
and this I2C bridge will "offload" this horrendous time
delay. :)

[kbanks]

Maxim IC I2C to 1 Wire bridge - DS2482.
The RF Engine should be able to read this I2C device?

If the device complies with the original I2C specs then SNAPpy should be able to talk to it.

It takes about 750 ms to read 1 Wire bus devices
and this I2C bridge will "offload" this horrendous time
delay.

Keep in mind it will take some time to do the I2C operations.